THIS FILE WAS ORIGINALLY POSTED ON OSUNY (914)428-7216,UNLESS OTHERWISE NOTED. SUFFICIENT CREDIT SHOULD BE GIVEN TOOSUNY WHEN POSTING THIS FILE ON OTHER SYSTEMS! So, you've decided that you'd like to try to down anRSTS system? Well, here's a beginner's guide: The RSTS system has two parts, the Priviledged accounts,and the User accounts. The Priviledged accounts start witha 1 (In the format [1,1], [1,10], etc. To show the Priv.accounts we'll just use the wildcard [1,*].) The priviledged accounts are what every RSTS user wouldlove to have, because if you have a priviledged accountyou have COMPLETE control of the whole system. How canI get a [1,*] account? you may ask....Well, it takes A LOTof hard work. Guessing is the general rule. for instance,when you first log in there will be a # sign: # (You type a [1,*] account, like) 1,2 It will then say Password: (You then type anything up to 6 letters/numbers Upper Case only) ABCDEF If it says ?Invalid Password, try again ' then you'venot done it YET...Keep trying. Ok, we'll assume you've succeeded. You are now inthe priviledged account of an RSTS system. The firstthing you should do is kick everyone else offthe system (Well, maybe just the other Priviledgedusers)....You do this with the Utility Program. UT KILL (here you type the Job # of the user you'dlike to get ut of your way). If the system won't letyou, you'll have to look for the UTILTY program. Searchfor it by typing DIR [1,*]UTILTY.*Now, you've found it and kicked off all the importantpeople (If you want you can leave the other peopleon, but it's important to remove all other [1,*] users,even the Detached ones). To find out who's who on thesystem type SYS/P- (That will print out allthe privileged users). Or type SYS to see Everyone. Next on your agenda is to get all the passwords(Of course). Do this by run$MONEY (If it isn't there,search for it with DIR[1,*]MONEY.* and run it usingthe account where you found it instead of the $) There will be a few questions, like Reset? andDisk? Here's the Important answers. Disk? SY (You want the system password) Reset? No (You want to leave everything as it is) Passwords? YES (You want the passwords Printed) There are others, but they aren't important, just hit a C/R. There is ONE more, it will say something like Output status to? KB: (This is important, youwant to see it, not send it elsewhere). Ok, now you've got all the passwords in your hands.Your next step is to make sure the next time youcome you can get in again. This is the hard part. First, in order to make sure that no one willdisturb you, you use the UTILTY program to make itso no one can login. Type UT SET NO LOGINS. (alsoyou can type UT HELP if you need help on the program)
Next you have to Change the LOGIN program....I'msorry, but this part is fuzzy, Personnally, I'venever gotten this far. Theorectically here's whatyou do: Find out where the program is, typeDIR [1,*]LOGIN.* If there is LOGIN.BAS anyplace,get into that account (Using your password list,and typing HELLO and the account you'd like toenter). On the DIR of the program there is a date(Like 01-Jan-80). To make it look good you typeUT DATE (and the date of the program).Next, you make it easy for yourself to access theprogram. You type PIP (And the account and name ofthe program you atre changeing) <60>=(again thename of the program). Now what you do is OLD the program. TypeOLD (Name of the program) Now that is all theoretical. If anyone runsinto problems, tell me about it and I'llsee if I can either figure it out or get someoneelse to. Next thing you want to do is LIST the program andfind out where The input of the Account # is.To get this far you have to knwo a lot about programmingand what to look for... Here is generally the idea, an idea is all it is,because I have not been able to field test it yet: Add a conditional so that if you type in a codeword and an account # it will respond with the password. This will take a while to look for, anda few minutes to change, but you can do it,you've got that RSTS system in your back pocket. Let's say you've (Somehow) been ableto change the program. The next thing you wantto do is replace it, so put it back whereyou got it (SAVE Prog-name), and the put itback to the Prot Level (The # in the <###>signs) by typing PIP (Prog name)<232>=Progname (Note, in all of this, don't use the ()'sthey are just used by me to show you what goeswhere). Now you've gotten this far, what do you do?I say, experiment! Look at all the programs, sinceyou have Privilged status you can analyze everyprogram. Look around forthe LOG program, andfind out what you can do to that. The last thing to do before youleave is to set the date back to what it was usingthe UTILTY program again UT DATE (and the current date). If you have any problems, questions, or experiences, don'tHesitate to write to me. I'd love to hear what you did. Sam Sneed
